Global cache tool systems and methods for adding new payees

ABSTRACT

Systems and methods for preparing payment requests via cached payee information databases are described. The cached payee database system allows customers of a financial institution to search locally stored payee databases on their mobile devices for payee information. The cache version of the payee database is periodically updated with new and corrected payee information. The cached database system can perform payee searches on a character-by-character basis in real time with minimal delays between searches.

FIELD

The present disclosure generally relates to online payment systems usingmobile devices.

BACKGROUND

With the growing prevalence of smartphones, tablets, and other compactmobile computing devices, many financial institutions have developedmobile banking software applications for their customers. These softwareapplications offer convenient ways for customers to perform increasinglycomplex banking transactions on their mobile devices. In turn, thesesoftware applications lower costs to financial institutions by reducingcustomer load on brick and mortar banking establishments. By theircompact nature, however, mobile devices possess limited hardware andnetworking capabilities relative to their desktop and laptopcounterparts. Maximizing the efficiency and ease of use of such mobilebanking applications is therefore an important priority for financialinstitutions in encouraging customers to use them.

SUMMARY

One embodiment relates to a financial institution computing system. Thesystem includes a payee database, a network interface logic, and a payeedatabase logic. The payee database logic is configured to maintain thepayee database. The payee database logic is further configured totransmit a cache version of the payee database through the networkinterface logic. The payee database logic is configured to receive aplurality of customer payment requests through the network interfacelogic wherein at least one payment request includes an intended payeeselected by a customer from the cache version of the payee database on acustomer device.

Another embodiment relates to a computer-implemented method. The methodincludes maintaining, by a payee database logic, a payee database havinga plurality of profiles of payee information associated with a pluralityof payees. The method further includes providing, by a financialinstitution, a customer device application that enables customers tosearch a cache version of the payee database and to transmit paymentrequests to the financial institution. The method includes transmitting,by a payee database logic through a network interface logic, a cacheversion of the payee database to a plurality of customer devices. Themethod further includes receiving, by the payee database logic throughthe network interface logic, a plurality of customer payment requestsfrom the plurality of customer devices, wherein at least one paymentrequest includes an intended payee selected by a customer from the cacheversion of the payee database on the customer's device.

An additional embodiment relates to a non-transitory computer readablemedia having computer-executable instructions embodied therein that,when executed by a payee database logic of a financial institutioncomputing system, cause the financial institution computing system toperform operations. The operations include maintain a payee databasehaving a plurality of profiles of payee information associated with aplurality of payees. The operations further include transmit a cacheversion of the payee database to a plurality of customer devices througha network interface logic. The operations include receive a plurality ofcustomer payment requests through the network interface logic wherein atleast one payment request includes an intended payee selected by acustomer from the cache version of the payee database on the customer'sdevice.

These and other features, together with the organization and manner ofoperation thereof, will become apparent from the following detaileddescription when taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a schematic diagram of a computer-implemented customer paymentrequest generating system according to an example embodiment.

FIGS. 2A and 2B are schematic diagrams of a mobile device bankingapplication according to an example embodiment.

FIG. 3 is a flow diagram of a method of updating payee informationdatabases according to an example embodiment.

DETAILED DESCRIPTION

Referring to the figures generally, systems and methods for preparingcustomer payment requests from customer mobile devices are described. Asystem and method for locally caching a financial institution's databaseof payee information on customers' mobile devices allows the financialinstitution's customers to quickly and accurately search for payees ontheir mobile devices. When a customer searches for a payee by enteringthe name of the payee into the customer's mobile device, the customer'smobile device populates a listing of possible payee matches by searchingthe locally cached database of payee information as each character ofthe intended payee's name is entered by the customer. By locally cachingthe database on the customer's mobile device instead of sending queriesto a remote payee database over a network, search results are returnedto the customer with minimal delay such that searches can be smoothlyrun in real time as customers enter each character into a search string.The speed with which the payee list is updated on the device display maytherefore keep up with the speed of data entry on the device keyboard.After a handful characters, the customer can select the desired payeefrom the search results and the payee's information in the database willthen be used to process the payment request. If there are too manysearch results, the customer can continue typing in characters until theintended payee appears. If the customer's desired payee is ultimatelynot found in the cached database, the customer can enter the payee'sfull payment information, which can then be used to update the payeedatabase for future use.

Referring to FIG. 1, a schematic diagram of a computer-implementedpayment request preparation system 100 is shown according to an exampleembodiment. System 100 provides banking services to customers of afinancial institution, including payment issuing services, via afinancial institution computing system 101 and mobile applications 108installed on customer mobile devices 102. Customers may be businessentities and/or individual persons having one or more accounts with thefinancial institution. Payees may be business entities or individualpersons. In some arrangements, a payee is an account holder with thefinancial institution. In other arrangements, a payee is not an accountholder with the financial institution. The financial institution is abanking entity capable of issuing payments from customer accountsmaintained by the financial institution to payees. The financialinstitution may be a commercial or private bank, a credit union, or aninvestment brokerage. Mobile applications 108 refer to software programsdesigned to operate on customer mobile devices 102. Mobile devices 102are portable computing devices that are capable of wirelessly accessingvarious types of data networks, and include smartphones, tablets, PDAs,and the like. The relationships between these various aspects of system100 are described in further detail below.

Still referring to FIG. 1, the financial institution computing system101 includes a payee database 103, payee database logic 104, and networkinterface logic 105. The payee database 103 contains profiles ofinformation for a plurality of payees, including, for example, eachpayee's full legal name, aliases, previous names, phone numbers,financial account information, and business addresses. The payeedatabase logic 104 maintains the payee database 103 and updates thepayee database 103 with corrected profile information (e.g., newaddresses, new aliases), and/or altogether new payee profiles. In somearrangements, the payee database logic 104 is executed by a processor(e.g., a processor of a backend server of the financial institutioncomputing system 101). A network interface logic 105 allows thefinancial institution computing system 101 to communicate with customermobile devices 102 over a network 106. The network interface logic 105may include network hardware, such as an Ethernet controller, thatallows the financial institution computing system 101 to send andreceive data over the network 106. The financial institution computingsystem 101 uses the network interface logic 105 to transmit the payeedatabase 103 and updates to the payee database 103 to customer mobiledevices 102 over a network 106, and to receive payment requests topayees from customer mobile devices 102. The network 106 may includewireless networks (e.g., cellular networks, Bluetooth, WiFi, Zigbee,etc.), wired networks (e.g., Ethernet, DSL, cable, fiber-based), or acombination thereof. In some arrangements, the network 106 includes theinternet. Although shown as being part of the financial institutioncomputing system 101, in some arrangements, the payee database 103 ismaintained by a third-party provider in communication with the financialinstitution computing system 101 via the network 106.

Still referring to FIG. 1, each customer mobile device 102 includes acache version of the payee database 107. The cache version of the payeedatabase 107 is stored in the mobile device's local storage (e.g.,integrated flash memory drives, SD cards, or other permanent orremovable storage drives), and reflects the information contained in thepayee database 103 in the financial institution computing system 101.The cache version of the payee database 107 is created based oninformation from the payee database 103. In some arrangements, the cacheversion of the payee database 107 is a condensed version of the payeedatabase 103. For example, the cache version of the payee database 107can be configured to include less than all of the payee information inthe payee database 103 (i.e., only a subset thereof, such as payeeaddresses only), and/or can be configured to include information in thepayee database 103 in an abbreviated format. For example, whereasinformation concerning the payees stored in the database 103 may includethe payee's name, aliases, previous names, phone numbers, addresses,financial account information, and the like, the cache version of thepayee database 107 may omit some of this information. The cache versionof the payee database 107 is transmitted from the financial institutioncomputing system 101 to the mobile devices 102 through the network 106.

The cache version of the payee database 107 is periodically updated toreflect new information in the payee database 103 in the financialinstitution computing system 101. After new or corrected information isadded to the payee database 103, the payee database logic 104 sends anupdate to the mobile devices 102 via the network interface logic 105.The update transmissions can be scheduled in several ways, for example,at predetermined time intervals (e.g., every twenty minutes), at thediscretion of the financial institution (i.e., on command), or on acontinuous basis as the payee database 103 itself is updated. The cacheversion of the payee database 107 can be updated via a full replacementof the cache version of the payee database 107 with information from thelatest version of the payee database 103, or by discrete corrections,additions, and deletions to payee profile information on the existingcopy of the cache version of the payee database 107.

Still referring to FIG. 1, customer mobile devices 102 also include amobile application 108, which is provided by the financial institution.The mobile application 108 can be provided, for example, in the form ofan “app” that customers can download from third-party vendors such asthe Apple App Store™ or Google Play™, or in the form of a mobile versionof the financial institution's website. The mobile application 108includes a graphical user interface that allows customers to performbanking functions through the financial institution computing system101. These banking functions include, for example, account balanceinquiries, balance transfers, and requests for payments to identifiedpayees. In performing these functions, the mobile application 108interfaces with a customer, the customer mobile device 102 itself, andthe financial institution computing system 101.

Referring to FIG. 2A, an example interactive graphical user interface200 of the mobile application 108 as viewed on a customer mobile device102 is shown according to an example embodiment. The user interface 200in FIG. 2A initially displays a welcome screen of the mobile application108. A customer can interact with the user interface 200 to performvarious banking functions, including paying bills by interacting withthe “Pay Bills” button 201 of the user interface 200. When a customerselects the “Pay Bills” button 201, the application 108 updates the userinterface 200 to allow the customer to enter payee information (e.g., asshown in FIG. 2B).

Referring to FIG. 2B, the user interface 200 of FIG. 2A has been updatedafter the customer interacted with the “Pay Bills” button 201 to an“Enter Payee Information” page 202. Through the user interface 200, acustomer can begin providing payee information (i.e., informationrelating to the intended recipient of funds from the customer's account)to the mobile application 108. As shown in FIG. 2B, the customer canstart typing the intended payee into the search query box 203 byinteracting with the user interface (e.g., by typing on a keyboard 204of the mobile device 102).

Still referring to FIG. 2B, based on the characters entered by thecustomer into the search query box 203, the mobile application 108 willsearch the cache version of the payee database 107 for payee profilescontaining matching payee information. Based on the search results, themobile application 108 updates a drop down list 205 of possible matchingpayees 206. The mobile application 108 repeatedly updates the search ofthe cache version of the payee database 107 and the identified payees inthe drop down list 205 with each keystroke of the customer on the mobilekeyboard 204. Accordingly, if the customer's intended payee appears inthe drop down list 205, the customer can select the intended payeewithout typing the full payee name, and the mobile application 108 canprepare the customer's payment to the intended payee using theinformation in the corresponding payee profile in the cache version ofthe payee database 107. If the customer's intended payee does not appearin the drop down list 205, or if the drop down list 205 is too long, thecustomer can keep typing additional characters of the intended payee'sname into the search query box 203 until the payee appears. In somesituations, the customer's intended payee is not contained in the cacheversion of the payee database 107, and will therefore not appear in thedrop down list 205 even after the customer enters the intended payee'sfull name. In these situations, the customer can add a new payee profileas described in further detail below.

The mobile application 108 can be configured such that it does not beginsearching the cache version of the payee database 107 until the customerhas entered a minimum number of characters (e.g., at least fourcharacters of a search string) into the search query box. Configuringthe mobile application 108 to require a minimum number of charactersbefore searching the cache version of the payee database 107 canincrease the efficiency of the payee selection process. If the mobileapplication 108 searches the cache version of the payee database 107after the customer has entered only a single letter into the searchquery box 203, such a search would likely return a large number ofirrelevant results and demand excessive processing power from thecustomer mobile device 102. These initial searches are thereforeunlikely to be useful, and the delays caused by the initial searches'demand on the mobile device's processing power will be inconvenient forthe customer. By configuring the mobile application 108 to require someminimum number of characters (i.e., greater than one character) beforethe mobile application 108 begins searching the cache version of thepayee database 107, the likelihood of returning relevant results isincreased, and the mobile application's demand on the mobile device'sprocessing power is reduced. As a result, the mobile application 108 canoperate more smoothly and provide the customer with more accurate searchresults.

The mobile application 108 can also be configured to incorporate acustomer's account information to sort or refine matching payees in thedrop down list 205. For example, a customer's account information caninclude that customer's name, addresses, phone numbers, and paymenthistory. The customer account information can also include thecustomer's demographic information, such as age, gender, ethnicity, andincome. Each of these pieces of customer information can be used tocategorize payees based on customer behavior (e.g., previous paymentrequests submitted by the financial institution's customers) andincrease search efficiency. For example, customer account informationcan be used to categorize popular payees by zip code or area code (asdetermined by previously submitted customer payment requests). Aftersearching for the characters in the search query entry box 203, themobile application 108 can further sort or refine the drop down list 205by popular payees by zip code and/or area code.

If the customer's desired payee is not stored in the cache version ofthe payee database 107, the mobile application 108 will not find amatching payee profile. In this case, the customer can manually enterall of the payee's information required for payment (e.g., the payee'sfull name, address, etc.) into the mobile application 108. The mobileapplication 108 can save the new payee's information as a new payeeprofile, and transmit the new payee profile back to the financialinstitution computing system 101 along with the customer's paymentrequest.

If the payee database logic 104 receives a payment request containing anew payee profile that the customer manually entered, the payee databaselogic 104 can determine whether the payee database 103 at the financialinstitution computing system 101 needs to be updated with the new payeeprofile. The payee database logic 104 can search for the new payeeprofile in the payee database 103. If the new payee profile does notexist in the payee database 103, the payee database logic 104 can addthe new payee profile and include the new payee profile in the nexttransmitted update to customer mobile devices 102. If the new payeeprofile already exists in the payee database 103, the payee databaselogic 104 will not need to take any additional actions regarding the newpayee profile.

The payee database 103 at the financial institution computing system 101can also be updated by the financial institution itself. The financialinstitution can enter corrected or new payee profile information to thepayee database logic 104 independently of whether new payee profiles orcorrected payee information is received from customer mobileapplications 108. The new and/or corrected payee profiles can then betransmitted to the customer mobile devices 102 as an update.

Referring to FIG. 3, a flow diagram of a method 300 of updating payeeinformation databases is shown according to an example embodiment. Themethod 300 is performed by a computer-implemented system of a financialinstitution (e.g., system 100), which provides a payment system thatallows customers to use mobile devices (e.g., mobile devices 102) toidentify payees and request the payment of funds to those payees fromthe customers' accounts. As discussed above with respect to system 100and in further detail below with respect to method 300, the financialinstitution's computing system (e.g., financial institution computingsystem 101) can be designed to operate with mobile software applications(e.g., mobile application 108) to allow customers to efficientlyidentify payees and prepare payment requests.

In method 300, a payee database is maintained by a financial institutioncomputing system (301). The financial institution computing systemmaintains the payee database by storing the information within, andrendering it accessible for various banking operations, includingprocessing payment requests. The payee database includes various typesof payee information sufficient to identify and send payments tospecific payees on behalf of the financial institution's customers,which are organized into payee profiles. The information in a givenpayee profile includes any of the payee's name, aliases, previous names,phone numbers, addresses, financial information, and the like. The payeeprofiles are stored as entries in the payee database, and are indexedsuch that the payee database is searchable by any of the types ofinformation collected to identify specific payees.

A mobile application (e.g., mobile application 108) is provided by afinancial institution to its customers (302). Mobile applications aresoftware programs intended to be operated on mobile devices such assmartphones, tablets, and PDAs (e.g., customer mobile device 102). Themobile application is provided in the form of an “app”, and can bedistributed to customers through third party vendors such as the AppleApp Store™ or Google Play™. Alternatively, the mobile application isprovided as a “mobile” version of the financial institution's websiteaccessed through web browsers of the customers' mobile computingdevices. The mobile application provides an interface for the financialinstitution and a customer to exchange information over a data network(e.g., network 106) using the customer's mobile device (e.g., customermobile device 102). Among various features, the mobile applicationallows customers to select payees and request the financial institutionto issue payments to selected payees from customer accounts with thefinancial institution.

The mobile application is designed to receive and cache a local copy ofthe payee database from the financial institution computing system. Themobile application caches the payee database in the mobile device'slocal memory (e.g., integrated memory drives, SD cards, etc.). Themobile application can receive the payee database through any of severaltypes of wired or wireless data networks (e.g., as described above withrespect to network 106).

The mobile application is further designed to search and pullinformation from the cached copy of the payee database on the customermobile device. As a customer enters each character into a search stringpresented by the mobile application, the mobile application searches thecache version of the payee database for payee profiles with matchinginformation. The mobile application may be configured to only beginsearching the cache version of the payee database after the customer hasentered some minimum number of characters, to prevent the applicationfrom returning an undesirably large number of results.

After the mobile application is provided at 302, a request for a copy ofthe payee database is received (303). The request is sent by the mobileapplication over a network and is received by the financial institutioncomputing system.

After the request is received at 303, a payee database is transmitted(304). The financial institution computing system transmits a copy ofthe payee database over a network to the customer's mobile device. In analternative arrangement, the payee database can be bundled with theprovided mobile application at 302. In such arrangements, the payeedatabase is simultaneously transmitted with the mobile application.

After the payee database is transmitted, the payee database is updated(305). The financial institution computing system updates the payeedatabase with any new payee profiles collected, and any corrections tothe information in previously generated payee profiles. For example,payees may change addresses, take on new aliases, change their phonenumbers, cease to exist, etc. Additionally, new payees may come intoexistence. The financial institution computing system updates the payeedatabase at the financial institution to reflect this new information ona periodic, discretionary, or continuous basis.

After the payee database logic updates the payee database at 305, thepayee database update is transmitted (306). The financial institutioncomputing system transmits the payee database update over a network toall customer devices that have the mobile application installed. Thefinancial institution computing system can transmit updates on a setperiodic basis (e.g., every 20 minutes), upon demand at the discretionof the financial institution, or continuously as new or correctedinformation is added to the payee database at the financial institution.The updates can be transmitted as complete replacement payee databases,or as discrete additions or corrections to the cache version of thepayee databases in customer devices.

The method can also update the payee database using information fromcustomer payment requests. For such an arrangement, a payment requestcan be received (307) at any point after the mobile application isprovided at 302. A customer mobile device can use the mobile applicationto send a payment request over a network, which is received by thefinancial institution computing system.

After a payment request is received at 307, the need for an update isdetermined (308). The financial institution computing system receives acustomer payment request sent over a network, and then searches thepayee database at the financial institution for the payee identified inthe payment request. If the payee identified in the payment request doesnot exist in the payee database, the financial institution computingsystem can update the payee database with a new payee profile with thepayee information from the payment request. The new payee profile canthen be included in the next payee database update transmitted tocustomer mobile devices. If the new payee profile already exists on thepayee database, the payee database logic will leave the payee databaseunmodified.

It should be noted that although the diagrams herein may show a specificorder and composition of method steps, it is understood that the orderof these steps may differ from what is depicted. For example, two ormore steps may be performed concurrently or with partial concurrence.Also, some method steps that are performed as discrete steps may becombined, steps being performed as a combined step may be separated intodiscrete steps, the sequence of certain processes may be reversed orotherwise varied, and the nature or number of discrete processes may bealtered or varied. The order or sequence of any element or apparatus maybe varied or substituted according to alternative embodiments.Accordingly, all such modifications are intended to be included withinthe scope of the present disclosure as defined in the appended claims.Such variations will depend on the software and hardware systems chosenand on designer choice. It is understood that all such variations arewithin the scope of the disclosure. Likewise, software and webimplementations of the present disclosure could be accomplished withstandard programming techniques with rule based logic and other logic toaccomplish the various database searching steps, correlation steps,comparison steps and decision steps.

As noted above, embodiments within the scope of this disclosure includeprogram products comprising non-transitory machine-readable media forcarrying or having machine-executable instructions or data structuresstored thereon. Such machine-readable media can be any available mediathat can be accessed by a general purpose or special purpose computer orother machine with a processor. By way of example, such machine-readableor non-transitory storage media can comprise RAM, ROM, EPROM, EEPROM,CD-ROM or other optical disk storage, magnetic disk storage or othermagnetic storage devices, or any other medium which can be used to carryor store desired program code in the form of machine-executableinstructions or data structures and which can be accessed by a generalpurpose or special purpose computer or other machine with a processor.Combinations of the above are also included within the scope ofmachine-readable media. Machine-executable instructions comprise, forexample, instructions and data which cause a general purpose computer,special purpose computer, or special purpose processing machines toperform a certain function or group of functions.

Embodiments have been described in the general context of method stepswhich may be implemented in one embodiment by a program productincluding machine-executable instructions, such as program code, forexample in the form of program modules executed by machines in networkedenvironments. Generally, program modules include routines, programs,objects, components, data structures, etc. that perform particular tasksor implement particular abstract data types. Machine-executableinstructions, associated data structures, and program modules representexamples of program code for executing steps of the methods disclosedherein. The particular sequence of executable instructions or associateddata structures represents examples of corresponding acts forimplementing the functions described in such steps.

As previously indicated, embodiments may be practiced in a networkedenvironment using logical connections to one or more remote computershaving processors. Those skilled in the art will appreciate that suchnetwork computing environments may encompass many types of computers,including personal computers, hand-held devices, multi-processorsystems, microprocessor-based or programmable consumer electronics,network PCs, minicomputers, mainframe computers, and so on. Embodimentsmay also be practiced in distributed computing environments where tasksare performed by local and remote processing devices that are linked(either by hardwired links, wireless links, or by a combination ofhardwired or wireless links) through a communications network. In adistributed computing environment, program modules may be located inboth local and remote memory storage devices.

An example system for implementing the overall system or portions of theembodiments might include a general purpose computing computers in theform of computers, including a processing unit, a system memory, and asystem bus that couples various system components including the systemmemory to the processing unit. The system memory may include read onlymemory (ROM) and random access memory (RAM). The computer may alsoinclude a magnetic hard disk drive for reading from and writing to amagnetic hard disk, a magnetic disk drive for reading from or writing toa removable magnetic disk, and an optical disk drive for reading from orwriting to a removable optical disk such as a CD ROM or other opticalmedia. The drives and their associated machine-readable media providenonvolatile storage of machine-executable instructions, data structures,program modules and other data for the computer. It should also be notedthat the word “terminal” as used herein is intended to encompasscomputer input and output devices. Input devices, as described herein,include a keyboard, a keypad, a mouse, joystick or other input devicesperforming a similar function. The output devices, as described herein,include a computer monitor, printer, facsimile machine, or other outputdevices performing a similar function.

The foregoing description of embodiments has been presented for purposesof illustration and description. It is not intended to be exhaustive orto limit the disclosure to the precise form disclosed, and modificationsand variations are possible in light of the above teachings or may beacquired from this disclosure. The embodiments were chosen and describedin order to explain the principals of the disclosure and its practicalapplication to enable one skilled in the art to utilize the variousembodiments and with various modifications as are suited to theparticular use contemplated. Other substitutions, modifications, changesand omissions may be made in the design, operating conditions andarrangement of the embodiments without departing from the scope of thepresent disclosure as expressed in the appended claims.

What is claimed is:
 1. A financial institution computing system forpreparing customer payment requests, the system comprising: a payeedatabase having a plurality of profiles of payee information associatedwith a plurality of payees; and a payee database logic configured to:transmit, via a network communicatively coupled to a customer compactmobile device, a cache version of the payee database associated with afinancial institution computing system to the customer compact mobiledevice, wherein the cache version of the payee database is configured tobe searched in response to at least one of a letter and a digit beingentered into a search query; receive, via an interactive graphical userinterface displayed by a mobile application of the customer compactmobile device, at least one customer payment request, wherein theinteractive graphical user interface is structured to receive a newpayee profile configured by the customer, and wherein a profile of anintended payee of the at least one customer payment request is notcontained in the cache version of the payee database; determine that thenew payee profile is not included in the payee database; update thepayee database to include the new payee profile; and transmit, via thenetwork communicatively coupled to the customer compact mobile device,an updated cache version of the payee database associated with thefinancial institution computing system to the customer compact mobiledevice, wherein the updated cache version of the payee database containsthe new payee profile.
 2. The system of claim 1, wherein the cacheversion of the payee database contains abbreviated payee informationfrom the payee database.
 3. The system of claim 1, wherein the cacheversion of the payee database is configured to be searched only if aminimum quantity of one or both of letters and digits of payeeinformation are entered into a search query.
 4. A computer implementedmethod of maintaining an updated payee database associated with afinancial institution computing system, the method comprising:maintaining, by a payee database logic, a payee database having aplurality of profiles of payee information associated with a pluralityof payees; providing, by a financial institution, a customer deviceapplication that enables customers to search a cache version of thepayee database and to transmit payment requests to the financialinstitution; transmitting, by the payee database logic through a networkcommunicatively coupled to a plurality of customer compact mobiledevices, one or more cache versions of the payee database to theplurality of customer compact mobile devices, wherein the cache versionsof the payee database are configured to be searched in response to atleast one of a letter and a digit being entered into a search query;receiving, by the payee database logic via an interactive graphical userinterface displayed by the customer device application on the pluralityof customer compact mobile devices, a plurality of customer paymentrequests from the plurality of customer compact mobile devices, whereinthe interactive graphical user interface is structured to receive a newpayee profile configured by a customer, and wherein a profile of anintended payee of at least one customer payment request of the pluralityof customer payment requests is not contained in the cache version ofthe payee database transmitted to the customer compact mobile devicefrom which the at least one customer payment request is received;determining that the new payee profile is not included in the payeedatabase; updating the payee database to include the new payee profile;and transmitting, via the network, an updated cache version of the payeedatabase associated with the financial institution computing system tothe customer compact mobile device, wherein the updated cache version ofthe payee database contains the new payee profile.
 5. The method ofclaim 4, wherein the cache version of the payee database containsabbreviated payee information from the payee database.
 6. The method ofclaim 4, wherein the cache version of the payee database is configuredto be searched only if a minimum quantity of one or both of letters anddigits of payee information are entered into a search query.
 7. Anon-transitory computer readable media having computer-executableinstructions embodied therein that, when executed by a payee databaselogic of a financial institution computing system, cause the financialinstitution computing system to perform operations to issue paymentsfrom customer accounts to identified payees, the operations comprising:maintain a payee database having a plurality of profiles of payeeinformation associated with a plurality of payees; transmit, via anetwork communicatively coupled to a customer compact mobile device, acache version of the payee database to compact mobile device, whereinthe cache version of the payee database is configured to be searched inresponse to at least one of a letter and a digit being entered into asearch query; receive, via an interactive graphical user interfacedisplayed by a mobile application of the customer compact mobile device,a plurality of customer payment requests, wherein the interactivegraphical user interface is structured to receive a new payee profileconfigured by the customer, and wherein a profile of an intended payeeof at least one customer payment request is not contained in the cacheversion of the payee database; determine that the new payee profile isnot included in the payee database; update the payee database to includethe new payee profile; and transmit, via the network communicativelycoupled to the customer compact mobile device, an updated cache versionof the payee database associated with the financial institutioncomputing system to the customer compact mobile device, wherein theupdated cache version of the payee database contains the new payeeprofile.
 8. The media of claim 7, wherein the cache version of the payeedatabase contains abbreviated payee information from the payee database.9. The media of claim 7, wherein the cache version of the payee databaseis configured to be searched only if a minimum quantity of one or bothof letters and digits of payee information are entered into a searchquery.
 10. The system of claim 1, wherein the cache version of the payeedatabase is structured to be searched according to customer accountinformation, the customer account information structured to categorizepayees to be displayed for selection as the intended payee based oncustomer behavior.
 11. The method of claim 4, wherein the cache versionof the payee database is structured to be searched according to customeraccount information, the customer account information structured tocategorize payees to be displayed for selection as the intended payeebased on customer behavior.
 12. The media of claim 7, wherein the cacheversion of the payee database is structured to be searched according tocustomer account information, the customer account informationstructured to categorize payees to be displayed for selection as theintended payee based on customer behavior.
 13. The system of claim 10,wherein the customer account information comprises a customer name,address, phone number, payment history, demographic information, or acombination thereof.
 14. The method of claim 11, wherein the customeraccount information comprises a customer name, address, phone number,payment history, demographic information, or a combination thereof. 15.The media of claim 12, wherein the customer account informationcomprises a customer name, address, phone number, payment history,demographic information, or a combination thereof.
 16. A customercompact mobile device comprising: a local memory; a cache version of apayee database stored on the local memory, the cache version of thepayee database being received, via a network communicatively coupled tothe customer compact mobile device, from a payee database, wherein thecache version of the payee database is configured to be searched inresponse to at least one of a letter and a digit being entered into asearch query; a customer device application received from a financialinstitution via the network communicatively coupled to the customercompact mobile device, the customer device application enabling acustomer to transmit payment requests to a financial institution via agraphical user interface displayed by the customer device application;wherein the customer compact mobile device is configured to: receive,via the graphical user interface of the customer device application, acustomer payment request entered by a user; receive, via a search querybox displayed the graphical user interface of the customer deviceapplication, letters entered by a user, the letters corresponding to anintended payee of the customer payment request; search the cache versionof the payee database based on the letters entered by the user; display,via the graphical user interface of the customer device application, alist of payee profiles, the list of payee profiles based on payeeprofiles stored in the cache version of the payee database that matchthe letters entered by the user; receive, via the graphical userinterface of the customer device application, a user selection of apayee profile from the list of payee profiles, the selected payeeprofile corresponding to the intended payee of the customer paymentrequest; and send, via the network communicatively coupled to thecustomer compact mobile device, the customer payment request and theselected payee profile to the financial institution.
 17. The device ofclaim 16, wherein the cache version of the payee database containsabbreviated payee information from the payee database.
 18. The device ofclaim 16, wherein the cache version of the payee database is configuredto be searched only if a minimum quantity of one or both of letters anddigits of payee information are entered into a search query.
 19. Thedevice of claim 16, wherein the cache version of the payee database isstructured to be searched according to customer account information, thecustomer account information structured to categorize payees to bedisplayed for selection as the intended payee based on customerbehavior.
 20. The device of claim 19, wherein the customer accountinformation comprises a customer name, address, phone number, paymenthistory, demographic information, or a combination thereof.